-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more how-to docs #41
Conversation
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
We should also include the latest guide we have from postlight about writing documentation for Mailchimp. Not a blocker for this issue but definitely something we should do. |
} | ||
``` | ||
|
||
Normally the `shop` relationship would result in a database query, but if `order` already has a `shopId` property, we can actually skip the database lookup because the client has requested only the `_id` property. There is a utility function that helps with this: `optimizeIdOnly`. Check out the `Query.viewer` resolver for an example of how to use it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should add link to the Query.viewer
resolver here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is that located?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Akarshit second request for clarification here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still going through the other files. This is awesome work! |
@Akarshit the Postlight documentation guide has been shared in notion for @zenweasel to check |
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
@MohanNarayana @delagroove @Akarshit Changes from C/R made. Please review |
## Events | ||
|
||
Developers are encouraged to add AppEvent emitters to their code whenever they create a serious event, allowing custom plugin authors to use this for extension | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can add this table here (if needed) and get rid of the dev concepts events doc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We absolutely do not want that table as it is very much out of date.
Closing in favor of creating smaller PR's |
Resolves: #34
Adds from old docs
How to:
Store custom fields on an order
Create an inventory plugin
Create a GraphQL query
Create a GraphQL mutation
Extend GraphQL to add field
Extend GraphQL with remote schema
Emit and Listen for Events (significantly rewritten)
Run Functions on Startup
Add Collections from a plugin
Write and run database migrations
Misc How to
Core:
Developing with GraphQL
New doc created from scratch:
How to extend a schema